Image generation-output control apparatus, method of controlling image generation-output control apparatus, and storage medium

ABSTRACT

An image generation-output control apparatus in an image processing system for controlling an image generation and output operation based on an instruction received from a server in the image processing system. The image generation-output control apparatus includes second circuitry including a plurality of second image drawing information generators, each having one or more capabilities compatible with one or more capabilities of a first image drawing information generator of a first circuitry of the server, to generate second image drawing information based on output target image information acquired from the server, an identifying unit to identify generator identification information used for identifying one of the plurality of second image drawing information generators, an identification information unit including the generator identification information associated with one of the plurality of the second image drawing information generators, and the identifying unit, and an identification information manager to manage the generator identification information.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority pursuant to 35 U.S.C. §119(a) toJapanese Patent Application No. 2016-039371, filed on Mar. 1, 2016 inthe Japan Patent Office, the disclosure of which is incorporated byreference herein in its entirety.

BACKGROUND

Technical Field

This disclosure relates to an image generation-output control apparatus,a method of controlling the image generation-output control apparatus,and a storage medium of a program of controlling the imagegeneration-output control apparatus.

Background Art

Systems that can define and control various processes for generating aprinted product by using a data format such as job definition format(JDF) are known. This system can collectively control various types ofprinters such as offset printers and digital printers. This system isreferred to as a hybrid work flow (HWF) system, and a server thatcontrols the HWF system is referred to as a HWF server.

In this HWF system, the offset printer including a raster imageprocessor (RIP) engine and the digital printer including a raster imageprocessor (RIP) engine are operated based on the same print data, inwhich the output result of the offset printer and the output result ofthe digital printer are required to be same in various properties suchas font, color tone, and layout. However, the RIP engine of the offsetprinter that generates raster data, which is to be used for the printingoperation, based on the print data, and the RIP engine of the digitalprinter that generates raster data, which is to be used for the printingoperation, based on the print data, are different RIP engines, andthereby the output result of the digital printer may become different.

The HWF system uses a plurality of RIP engines in some cases. Forexample, when the program used for RIP engine is changed from oneversion to another version, the program of one version and the programof another version may coexist as disclosed in JP-2012-108821-A, inwhich raster data processed by the RIP engine of one version and rasterdata processed by the RIP engine of another version are compared toevaluate differences of the raster data.

When the offset printer outputs an image in the HWF system, a RIP enginedisposed in the HWF server generates raster data (hereinafter, RIPprocessing), and transmits the raster data to a computer-to-plate (CTP)of the offset printer that generates a plate to be used at the offsetprinter. Further, when the digital printer outputs an image in the HWFsystem, a digital front end (DFE) of the digital printer receives printdata and performs the RIP processing, and then a printer engine performsthe printing operation.

Therefore, it is required that the process result of the RIP engine thatgenerates the data to be transferred to the CTP and the process resultof the RIP engine of the DFE become the same as much as possible.

However, JP-2012-108821-A does not consider the RIP engine installed inthe DFE. Therefore, when the version of the RIP engine installed in theHWF server and the version of the RIP engine installed in the DFE aredifferent, the printing result may become different.

SUMMARY

As one aspect of the present invention, an image generation-outputcontrol apparatus in an image processing system for controlling an imagegeneration and output operation based on an instruction received from aserver in the image processing system is devised. The server controls aplurality of processes performable by the image processing system, andis communicable with a first image forming apparatus and a second imageforming apparatus in the image processing system, the server includingfirst circuitry including a first image drawing information generator togenerate first image drawing information based on output target imageinformation when performing an image forming operation for the outputtarget image information using the first image forming apparatus. Theimage generation-output control apparatus includes second circuitryincluding a plurality of second image drawing information generators,each having one or more capabilities compatible with one or morecapabilities of the first image drawing information generator of thefirst circuitry of the server, to generate second image drawinginformation based on the output target image information acquired fromthe server, an identifying unit to identify generator identificationinformation used for identifying one of the plurality of second imagedrawing information generators, an identification information unitincluding the generator identification information associated with oneof the plurality of the second image drawing information generators, andthe identifying unit, and an identification information manager tomanage the generator identification information. The identificationinformation unit instructs the identifying unit to identify thegenerator identification information when the server transmits anacquisition request for the generator identification information to theimage generation-output control apparatus. The identificationinformation manager manages the identified generator identificationinformation by including the identified generator identificationinformation in job information of the image generation-output controlapparatus.

As another aspect of the present invention, a method of controlling animage generation and output operation by using an imagegeneration-output control apparatus in an image processing system basedon an instruction received from a server in the image processing systemis devised. The server controls a plurality of processes performable bythe image processing system, and is communicable with a first imageforming apparatus and a second image forming apparatus in the imageprocessing system, the server including first circuitry including afirst image drawing information generator to generate first imagedrawing information based on output target image information whenperforming an image forming operation for the output target imageinformation using the first image forming apparatus. The imagegeneration-output control apparatus includes second circuitry includinga plurality of second image drawing information generators, each havingone or more capabilities compatible with one or more capabilities of thefirst image drawing information generator of the first circuitry of theserver, to generate second image drawing information based on the outputtarget image information acquired from the server. The method includesidentifying generator identification information for identifying one ofthe second image drawing information generators based on an acquisitionrequest for the generator identification information received from theserver, and managing the identified generator identification informationby including the identified generator identification information in jobinformation of the image generation-output control apparatus.

As another aspect of the present invention, a non-transitory storagemedium storing a program that, when executed by a computer, causes thecomputer to execute a method of controlling an image generation andoutput operation by using an image generation-output control apparatusin an image processing system based on an instruction received from aserver in the image processing system is devised. The server controls aplurality of processes performable by the image processing system, andis communicable with a first image forming apparatus and a second imageforming apparatus in the image processing system, the server includingfirst circuitry including a first image drawing information generator togenerate first image drawing information based on output target imageinformation when performing an image forming operation for the outputtarget image information using the first image forming apparatus. Theimage generation-output control apparatus includes second circuitryincluding a plurality of second image drawing information generators,each having one or more capabilities compatible with one or morecapabilities of the first image drawing information generator of thefirst circuitry of the server, to generate second image drawinginformation based on the output target image information acquired fromthe server. The method includes identifying generator identificationinformation for identifying one of the second image drawing informationgenerators based on an acquisition request for the generatoridentification information received from the server, and managing theidentified generator identification information by including theidentified generator identification information in job information ofthe image generation-output control apparatus.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete appreciation of the description and many of theattendant advantages and features thereof can be readily obtained andunderstood from the following detailed description with reference to theaccompanying drawings, wherein:

FIG. 1 is a schematic diagram illustrating a configuration of a systemof an embodiment of the present invention;

FIG. 2 is a schematic diagram illustrating a hardware configuration ofan information processing apparatus of an embodiment of the presentinvention;

FIG. 3 is an example of JDF information of an embodiment of the presentinvention;

FIG. 4 is a schematic diagram illustrating a functional configuration ofa HWF server of an embodiment of the present invention;

FIG. 5 is an example of workflow information of an embodiment of thepresent invention;

FIG. 6 is a schematic diagram illustrating a functional configuration ofa DFE of an embodiment of the present invention;

FIG. 7 is an example of a conversion table of an embodiment of thepresent invention;

FIG. 8 is an example of RIP parameter of an embodiment of the presentinvention;

FIG. 9 is a schematic diagram illustrating a functional configuration ofa RIP engine of an embodiment of the present invention;

FIG. 10 is a schematic diagram illustrating another functionalconfiguration of a RIP engine of an embodiment of the present invention;

FIG. 11 is a sequential chart for an operation flow of a HWF system ofan embodiment of the present invention;

FIG. 12 illustrates an example of a dividing pattern of image data;

FIG. 13 is a flow chart showing the steps of processing in the DFE of anembodiment of the present invention;

FIG. 14 is flow chart showing the steps of RIP processing of anembodiment of the present invention;

FIG. 15 illustrates an example of configuration of RIP engines disposedin the DFE of an embodiment of the present invention;

FIG. 16 is a fictional block diagram of a vendor information managementunit of an embodiment of the present invention;

FIG. 17 illustrates an example of contents of RIP device information ofan embodiment of the present invention; and

FIG. 18 is a sequential chart indicating a flow of a process comparingversions of RIP engines at a HWF server of an embodiment of the presentinvention;

The accompanying drawings are intended to depict exemplary embodimentsof the present invention and should not be interpreted to limit thescope thereof. The accompanying drawings are not to be considered asdrawn to scale unless explicitly noted, and identical or similarreference numerals designate identical or similar components throughoutthe several views.

DETAILED DESCRIPTION

A description is now given of exemplary embodiments of presentdisclosure. It should be noted that although such terms as first,second, etc. may be used herein to describe various elements,components, regions, layers and/or sections, it should be understoodthat such elements, components, regions, layers and/or sections are notlimited thereby because such terms are relative, that is, used only todistinguish one element, component, region, layer or section fromanother region, layer or section. Thus, for example, a first element,component, region, layer or section discussed below could be termed asecond element, component, region, layer or section without departingfrom the teachings of present disclosure.

In addition, it should be noted that the terminology used herein is forthe purpose of describing particular embodiments only and is notintended to be limiting of present disclosure. Thus, for example, asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. Moreover, the terms “includes” and/or “including”, when usedin this specification, specify the presence of stated features,integers, steps, operations, elements, and/or components, but do notpreclude the presence or addition of one or more other features,integers, steps, operations, elements, components, and/or groupsthereof.

Furthermore, although in describing views illustrated in the drawings,specific terminology is employed for the sake of clarity, the presentdisclosure is not limited to the specific terminology so selected and itis to be understood that each specific element includes all technicalequivalents that operate in a similar manner and achieve a similarresult. Referring now to the drawings, one or more apparatuses orsystems according to one or more embodiments are described hereinafter.

A description is given of an image processing system of one or moreembodiments of present disclosure with reference to drawings. The imageprocessing system includes, for example, an offset printer, and adigital printer, and a server, in which both of the offset printer andthe digital printer can be controlled by the same server. Hereinafter,this image processing system is referred to a hybrid work flow (HWF)system. In the HWF system, a raster image processor (RIP) enginedisposed in a digital front end (DFE) that controls the digital printer,and a raster image processor (RIP) engine disposed in the HWF server canemploy the same type of RIP engine, and the digital printer executes aprinting operation in this HWF system under the condition that the sametype of RIP engine is disposed at the different apparatuses configuringthe HWF system. In this disclosure, the same type of RIP engine may meantwo or more RIP engines have substantially same processing capabilities,and thereby the two or more RIP engines are not required to have theexact same processing capabilities.

FIG. 1 is a schematic configuration of the HWF system of one or moreembodiments of present disclosure. As illustrated in FIG. 1, the HWFsystem includes, for example, a digital printer 1, an offset printer 2,a post-processing apparatus 3, HWF servers 4 a and 4 b (hereinafter,collectively referred to HWF server 4 as required), and client terminals5 a and 5 b (hereinafter, collectively referred to client terminal 5 asrequired) connectable or couplable with one to another via a network.The offset printer 2 is used as a first image forming apparatus, and thedigital printer 1 is used as a second image forming apparatus in presentdisclosure.

The digital printer 1 is an example of printers that can generate andoutput images using an electrophotography method or an inkjet methodwithout using a plate. The digital printer 1 includes, for example, adigital front end (DFE) 100, and a digital engine 150 as indicated inFIG. 1. The DFE 100 can be used as a controller for controlling an imagegeneration and output, which means the DFE 100 can be used as an imagegeneration-output control apparatus, in which the DFE 100 controls thedigital engine 150 to perform a print output operation or printingoperation. Further, the digital engine 150 can be used as a device forgenerating an image, which may be referred to as an image generator orprint engine. Therefore, the DFE 100 includes a raster image processor(RIP) engine that generates raster data that is referred or used by thedigital engine 150 when performing the print output operation. Theraster data is used as drawing information or image drawing information.

The offset printer 2 is an example of printers that can generate andoutput images by using a plate. The offset printer 2 includes, forexample, a computer-to-plate (CTP) 200, and an offset engine 250. TheCTP 200 generates a plate based on the raster data. The offset engine250 can perform an offset printing by using the plate generated by theCTP 200.

The post-processing apparatus 3 can perform various post-processing suchas punch, staple, and bookbinding to printed sheets output from thedigital printer 1 and/or the offset printer 2. Further, thepost-processing apparatus 3 can perform a sheet folding and sheetcutting when the offset printer 2 outputs sheets processed with theimposition.

The HWF server 4 further includes a raster image processor (RIP) enginein the HWF server 4. When the offset printer 2 performs an offsetprinting operation (i.e., print output operation), the RIP engine 420 inthe HWF server 4 generates raster data, and transmits the generatedraster data to the CTP 200, in which the RIP engine 420 generates theraster data as first image drawing information. The offset printer 2 isused as the first image forming apparatus, and the RIP engine 420installed in the HWF server 4 can be used as a control-side imagedrawing information generator, a control-side drawing informationgenerator or a first image drawing information generator that generatesthe first image drawing information.

Further, when the digital printer 1 performs a printing operation (i.e.,print output operation), the HWF server 4 transmits data to the DFE 100.Since the DFE 100 has the RIP engine 120 as described above, the digitalprinter 1 can perform the print output operation even when the HWFserver 4 transmits print data that is not processed by the RIPprocessing in the HWF server 4 to the DFE 100. The digital printer 1 isused as the second image forming apparatus, and the RIP engine 120installed in the DFE 100 can be used as an output-side image drawinginformation generator, an output-side drawing information generator or asecond image drawing information generator that generates second imagedrawing information.

As to the HWF system, the same print data may be used for the printoutput operation by the digital printer 1 and the print output operationby the offset printer 2. For example, one book can be printed by theprint output operation of the digital printer 1 and the print outputoperation by the offset printer 2, in which the print output operationby the digital printer 1 and the print output operation by the offsetprinter 2 are performed independently. In this configuration, if theprint output operation result by the digital printer 1 and the printoutput operation result by the offset printer 2 become different such asdifferent fonts and color values, a user feels oddness on a printedproduct. Therefore, it is preferable that the print output operationresult by the digital printer 1 and the print output operation result bythe offset printer 2 become substantially the same one.

The differences of print output operation results by using differentdevices or apparatuses may occur due to the RIP processing. Therefore,by using the same RIP engine for data or information processing at thedigital printer 1 and data or information processing at the offsetprinter 2, the differences between the print output operation result bythe digital printer 1 and the print output operation result by theoffset printer 2 can be reduced or minimized.

Specifically, the RIP engine disposed in the HWF server 4 is an enginethat can process data or information for both of the digital printer 1and the offset printer 2, and the RIP engine disposed in the HWF server4 can perform common processes for the digital printer 1 and the offsetprinter 2. Further, the RIP engine disposed in the DFE 100 and the RIPengine disposed in the HWF server 4 employ the same type of RIP engine,which means that the RIP engine disposed in the DFE 100 is compatiblewith the RIP engine disposed in the HWF server 4.

With employing this configuration, the HWF server 4 and the DFE 100 aredisposed with the same RIP engine having the same processing capability.Therefore, when the print output operation by the digital printer 1 isto be performed, the RIP processing by the HWF server 4 and the RIPprocessing by the DFE 100 can be selectively combined and performed.

An operator of the HWF system can operate the HWF server 4 by using theclient terminal 5, in which the client terminal 5 can be used as aninformation processing terminal. The client terminal 5 can be anyterminal devices or apparatuses such as a general personal computer(PC), but not limited hereto. The operator operates the client terminal5 to display a graphic user interface (GUI) used for operating the HWFserver 4, in which the GUI can be used to input data and setting the JDFinformation. The JDF information sets information for processing in theHWF system, and the JDF information may be referred to as processsetting information.

A description is given of a hardware configuration of the DFE 100, theHWF server 4, and the client terminal 5 known as information processingapparatuses with reference to FIG. 2. As illustrated in FIG. 2, theinformation processing apparatus has a configuration similar to generalservers and personal computers (PC). Specifically, the informationprocessing apparatus includes, for example, a central processing unit(CPU) 10, a random access memory (RAM) 20, a read only memory (ROM) 30,a hard disk drive (HDD) 40, and an interface (I/F) 50 that areconnectable or couplable by a bus 80. Further, a liquid crystal display(LCD) 60 and an operation unit 70 are connectable or couplable to theinterface I/F 50.

The CPU 10 is a computing unit such as circuitry or a processor thatcontrols the entire operations of the information processing apparatus.The RAM 20 is a volatile memory, to which information can be read andwritten with high speed, and the CPU 10 uses the RAM 20 as a workingarea when processing information or data. The ROM 30 is a non-volatilememory used as a read only memory, in which various programs such asfirmware are stored. The HDD 40 is a non-volatile memory, to whichinformation can be read and written. For example, the HDD 40 stores anoperating system (OS), various control programs, and applicationprograms.

The I/F 50 is connected or coupled to the bus 80, various units andnetworks, and controls the connection or coupling. The LCD 60 is a userinterface that a user can check the status of the information processingapparatus visually. The operation unit 70 is a user interface such as akey board and a mouse that a user can input information to theinformation processing apparatus. Since the HWF server 4 is used as aserver, a user interface such as LCD 60 and operation unit 70 can beomitted for the HWF server 4.

As to the above described hardware configuration of the informationprocessing apparatus, the CPU 10 performs computing by loading programsstored in the ROM 30, the HDD 40, and/or an external memory such as anoptical disk on the RAM 20 to configure a software control unit. With acombination of the software control unit and the hardware, functionalblocks required for the DFE 100, the HWF server 4, and the clientterminal 5 can be devised.

A description is given of the JDF information with reference to FIG. 3.FIG. 3 is an example of the JDF information. As illustrated in FIG. 3,the JDF information includes, for example, “job information” related toa job execution, “edit information” related to the raster data, and“finishing information” related to the post-processing. Further, the JDFinformation includes, for example, information of “RIP status,” “RIPdevice designation,” and “device designation.”

As illustrated in FIG. 3, the “job information” includes information of,for example, “number of copies,” “number of total pages,” and “RIPcontrol mode.” The “number of copies” is information that designates thenumber of copies of an output target data to be output as a printedproduct. The “number of total pages” is information that designates thenumber of total pages included in one printed product. The “RIP controlmode” indicates a control mode of the RIP processing, in which a “pagemode” and a “sheet mode” can be designated for the “RIP control mode.”

The “edit information” includes, for example, “orientation information,”“print face information,” “rotation,” “enlarge/reduce,” “imageposition,” “layout information,” “margin information,” and “crop markinformation.” The “orientation information” is information thatdesignates a printing orientation of a sheet such as “portrait(vertical)” and “landscape (horizontal).” The “print face information”is information that designates a to-be-printed face such as “duplex” and“one face.”

The “rotation” is information that designates a rotation angle of animage of an output target data. The “enlarge/reduce” is information thatdesignates a size change ratio of an image of an output target data. Asto the “image position,” “offset” is information that designates anoffset of an image of an output target data, and “position adjustmentinformation” is information that designates a position adjustment valueof an image of an output target data.

The “layout information” includes, for example, “custom impositionarrangement,” “number of pages,” “page sequence information,” and “creepposition information.” The “custom imposition arrangement” isinformation that designates an arrangement on a custom face. The “numberof pages” is information that designates the number of pages printed inone sheet. For example, when images of two pages are condensed andprinted on one face of a single sheet, information of “2 in 1” isdesignated. The “page sequence information” is information thatdesignates a sequence of pages to be printed. The “creep positioninformation” is information that designates a value related to anadjustment of a creep position.

The “margin information” is information that designates a value relatedto a margin such as a fit box and a gutter. The “crop mark information”includes, for example, “center crop mark information” and “corner cropmark information.” The “center crop mark information” is informationthat designates a value related to a center crop mark. The “corner cropmark information” is information that designates a value related to acorner crop mark.

The “finishing information” includes, for example, “Collateinformation,” “staple/binding information,” “punch information,”“folding information,” “trimming,” “output tray information,” “inputtray information,” and “cover sheet information.” The “Collateinformation” is information that designates a page-by-page printing or adocument-by-document printing when one document is to be printed with aplurality of numbers of copies.

The “staple/binding information” is information that designates aprocess related to staple/binding. The “punch information” isinformation that designates a process related to punch. The “foldinginformation” is information that designates a process related to foldingof sheets. The “trimming” is information that designates a processrelated to trimming of sheets.

The “output tray information” is information that designates an outputtray. The “input tray information” is information that designates aninput tray. The “cover sheet information” is information that designatesa process related to a cover sheet.

The “RIP status” is used as execution status information indicatingwhether each of internal processes included in the RIP processing isalready executed. In an example case of FIG. 3, the internal processesof RIP processing includes items such as “pre-fright,” “normalize,”“font,” “layout,” “mark,” “CMM,” “Trapping,” “Calibration,” and“Screening,” and a processing status is set for each of the internalprocesses of RIP. In the example case of FIG. 3, the processing statusof “NotYet” is set for the “RIP status” to indicate that “a concernedprocess is not yet processed”. When each of the internal processes ofRIP is executed, the status is updated to “Done” to indicate that “theconcerned process is already processed.”

The “RIP device designation” is information that designates a device toperform each of the internal processes of RIP processing. In the examplecase of FIG. 3, the “RIP device designation” designates the HWF server 4or the DFE 100 to perform each of the internal processes of RIPprocessing. As illustrated in FIG. 3, each one of the internal processesof RIP processing is performed by setting any one of the “HWF server”and “DFE” for each of the internal processes of RIP processing. Further,when the “DFE” is set as the RIP device, information designating any oneof a plurality of RIP engines installed in the DFE 100 can be designatedsuch as “DFE (engine A)” and DFE (engine B).

The “device designation” is information that designates a device thatexecutes a print job. In the example case of FIG. 3, the “digitalprinter” is designated to execute the print job. Further, the JDFinformation can include various information other than informationillustrated in FIG. 3, which will described later in this disclosure.

The JDF information illustrated in FIG. 3 can be generated by anoperator. For example, the operator operates the client terminal 5 todisplay a GUI of the HWF server 4, and then the operator sets variousitems of the JDF information by using the GUI. The RIP engine disposedin the HWF server 4 and the RIP engine disposed in the DFE 100 canperform the RIP processing based on the JDF information. Further, thepost-processing apparatus 3 can perform the post-processing based on theJDF information. Further, when a job is input to the HWF server 4 froman external system and software, the job assigned with JDF informationmay be input.

A description is given of a fictional block diagram of the HWF server 4with reference to FIG. 4. As illustrated in FIG. 4, the HWF server 4includes, for example, a HWF controller 400, and a network interface(I/F) 401. The network I/F 401 is an interface used for communicatinginformation between the HWF server 4 and other devices or apparatusesavailable for use via a network.

The HWF controller 400 manages various processing such as an acquisitionof job data of a print target, a generation of a print job, a managementof a workflow, and an allocation of job data to the digital printer 1and the offset printer 2. A process that job data of a print target isinput to the HWF server 4 and acquired by the HWF controller 400 is aprocess of inputting data to the HWF system. The HWF controller 400 canbe implemented by installing a specific software program such as a HWFsoftware program in the information processing apparatus.

As illustrated in FIG. 4, the HWF controller 400 includes, for example,a system controller 410, a data receiver 411, a user interface (UI)controller 412, a job controller 413, a job data storage 414, a deviceinformation communication unit 415, a device information manager 416, adevice information storage 417, a workflow controller 418, a workflowinformation storage 419, a RIP engine 420, and a job communication unit421. The system controller 410 controls the HWF controller 400 entirely.Therefore, the system controller 410 transmits commands to each of theunits in the HWF controller 400 to implement each of the above describedfunctions or capabilities of the HWF controller 400. The data receiver411 receives to-be-printed job data from other system, or to-be-printedjob data input by an operation of an operator.

The UI controller 412 controls an operation operable by an operator viathe client terminal 5. For example, a graphical user interface (GUI)used for operating the HWF server 4 is displayed on the client terminal5, and the UI controller 412 acquires information of an operation workto the GUI displayed on the client terminal 5 via a network.

The UI controller 412 reports information of the operation acquired viathe network to the system controller 410. The display of GUI on theclient terminal 5 can be implemented by executing a software programinstalled in the client terminal 5, or by supplying information to theclient terminal 5 from the UI controller 412 via the network.

The operator operates the GUI displayed on the client terminal 5 toselect job data to be input as a print target. Then, the client terminal5 transmits the selected job data to the HWF server 4, and then the datareceiver 411 acquires the selected job data. The system controller 410registers the job data acquired by the data receiver 411 to the job datastorage 414.

When the job data is to be transmitted from the client terminal 5 to theHWF server 4, the job data is generated in the client terminal 5 basedon document data and/or image data selected at the client terminal 5,and then the job data is transmitted to the HWF server 4. The job datais described, for example, by page description language (PDL) formatsuch as portable document format (PDF) and PostScript.

Further, the client terminal 5 can transmit data of a print target tothe HWF server 4 by using an application specific data format or ageneral image data format. In this configuration, the system controller410 instructs the job controller 413 to generate job data based on theacquired data. The job controller 413 generates the job data based onthe data of print target by using the RIP engine 420.

As described above, the data of print target registered in the job datastorage 414 is PDL information. The PDL information can be, for example,primary data generated from the data of print target, or intermediatedata, which is processed to the middle of the RIP processing. Theseinformation can be used as information of an output target image (i.e.,output target image information). For example, the intermediate data canbe stored in the job data storage 414 when the job data is processed tothe middle of the RIP processing that is already started in the HWFserver 4, or when the job data is registered in the HWF server 4 with acondition of the intermediate data. Hereinafter, the “PDL information”indicates primary data that is not yet processed by the RIP processing,and the intermediate data indicates data that is processed to the middleof the RIP processing (i.e., processing-not-completed data) in thisdisclosure.

Further, as described above, the JDF information illustrated in FIG. 3can be set and generated by an operation of an operator to the GUIdisplayed on the client terminal 5. Further, when a job is input to theHWF server 4 from an external system and software, the JDF informationmay be assigned to the job. The generated or acquired JDF informationcan be received by the data receiver 411 with the PDL information as thejob data. The system controller 410 correlates the acquired JDFinformation and PDL information, and registers the JDF information andPDL information to the job data storage 414.

In this disclosure, attribution information indicating job contents isdescribed by using the JDF information, but not limited hereto. Forexample, the attribution information indicating job contents can bedescribed by using other format such as print production format (PPF).

Further, the system controller 410 can divide the received job data asrequired based on an operation of an operator to a GUI displayed on theclient terminal 5. For example, the system controller 410 can divide thereceived job data into a discrete unit of printing portion such as aunit of “page,” and each one of the divided job data can be registeredin the job data storage 414 as sub job data, in which the job data isconfigured by the plurality of the sub-job data.

When an output-destination device is selected for each of the sub jobdata by an operation of an operator to a GUI displayed on the clientterminal 5, the operator's selection result is correlated with thesub-job data, and then stored in the job data storage 414. Theoutput-destination device can be set selectively for each of the sub jobdata. For example, the digital printer 1 can be selected for printingsub job data corresponding to a cover of the received job data, and theoffset printer 2 can be selected for printing sub-job data correspondingto a main contents of the received job data.

The device information manager 416 acquires information of availabledevices or apparatuses included in the HWF system such as the digitalprinter 1, the offset printer 2, the post-processing apparatus 3 or thelike, and the device information manager 416 stores information of theavailable devices or apparatuses in the device information storage 417,and manages the information of the available device or apparatuses. Theinformation of available devices includes, for example, a networkaddress allocated to each device when the device is connected or coupledto the network, and device capability information of each device. Thedevice capability information includes, for example, printing speed,available post-processing capability, and operational condition.

The device information communication unit 415 can acquire information ofthe available devices included in the HWF system at regular intervalsvia the network I/F 401. With this configuration, the device informationmanager 416 can update information of the available devices stored inthe device information storage 417 at regular intervals. Therefore, evenif the information of the available devices changes over time, theinformation stored in the device information storage 417 can be updatedand maintained at the latest status.

The workflow controller 418 determines an execution sequence of aplurality of processes to be executed for the job data registered in thejob data storage 414 in the HWF system, and stores information of theexecution sequence in the workflow information storage 419. Based on theexecution sequence set for each of processes in a workflow in advance,the workflow controller 418 can control the execution sequence, in whichwhen one process completes, the sequence proceeds to the next process.

The workflow information stored in the workflow information storage 419specifies the execution sequence of each of processes executable in theHWF system, in which the processes are sequentially arranged based onthe designated execution sequence. FIG. 5 is an example of workflowinformation. Further, parameters, which are used when each of theprocesses is executed, can be designated as the JDF information as abovedescribed. The workflow information storage 419 registers the workflowinformation in advance based on an operation of an operator to the GUIdisplayed on the client terminal 5.

An execution instruction of the job data, registered in the HWF server4, is reported to the system controller 410 via the UI controller 412based on an operation of an operator to the GUI displayed on the clientterminal 5. With this configuration, the system controller 410 canselect the above described output-destination device.

When the output-destination device is selected by using the GUIdisplayed on the client terminal 5 as described above, the systemcontroller 410 selects the output-destination device based on adesignation of the output-destination device. Further, theoutput-destination device can be selected automatically based on acomparison of job contents and a device property.

When the output-destination device is selected automatically based onthe comparison of job contents and the device property, the systemcontroller 410 acquires information of device available for use from thedevice information manager 416. When the output-destination device isdetermined as above described, the system controller 410 assignsinformation indicating the determined output-destination device to theJDF information.

After determining the output-destination device, the system controller410 instructs the workflow controller 418 to execute a job. In thisprocess, the workflow information, registered in the workflowinformation storage 419 in advance based on then operation of theoperator, can be used. Further, a new workflow information can begenerated and then used based on contents set by the operator.

After receiving the execution instruction from the system controller410, the workflow controller 418 instructs the job controller 413 toexecute each of the processes based on the designated execution sequenceof the designated workflow information or the newly generated workflowinformation. Therefore, the workflow controller 418 can be used as aprocess execution controller.

After receiving the execution instruction, the job controller 413 inputsthe above described PDL information and JDF information to the RIPengine 420 to execute the RIP processing. The JDF information includesinformation that indicates which one of the HWF server 4 and the DFE 100is used for processing each of internal processes of the RIP processingusing the RIP engine.

The job controller 413 refers or checks allocation information of theRIP processing included in the JDF information. If one processdesignated by the workflow controller 418 is a process to be executed bythe HWF server 4, the job controller 413 instructs the RIP engine 420 toexecute the designated one process. Based on the instruction from thejob controller 413, the RIP engine 420 executes the RIP processing basedon parameters designated in the JDF information.

After executing the RIP processing, the RIP engine 420 updates the RIPstatus of each of the processes executed by the RIP processing. Withthis configuration, the status of each of the internal processes of theRIP processing executed by the HWF server 4 is changed from “NotYet” to“Done.” The RIP engine 420 can be used as a control-side image drawinginformation generator, a control-side drawing information generator or afirst image drawing information generator.

The RIP-executed result data generated by executing the RIP processingis any one of PDL information, intermediate data, and raster data. Anyone of the PDL information, intermediate data, or raster data can begenerated depending on the internal process of the RIP processing.Specifically, as the sequence proceeds, the intermediate data isgenerated from primary data such as PDL information, and the raster datais generated as final data from the intermediate data. The RIP-executedresult data is correlated with a being-executed job, and stored in thejob data storage 414.

When each one of the internal processes of RIP processing is completed,the RIP engine 420 reports the completion of each one of the internalprocesses to the job controller 413, and the job controller 413 reportsthe completion of each one of the internal processes to the workflowcontroller 418. With this configuration, the workflow controller 418starts to control a subsequent or next process based on the workflowinformation.

If the job contents received from the workflow controller 418 is arequest to the other system, the job controller 413 inputs job data,compatible with the other system, to the job communication unit 421, andinstructs the job communication unit 421 to transmit the job data. Ifthe job data is to be transmitted to the offset printer 2, the job dataof a print target is converted to the raster data, and then the rasterdata is transmitted to the offset printer 2 as the job data.

Further, if the job data is to be transmitted to the digital printer 1,the job controller 413 inputs the job data to the job communication unit421 while designating a RIP engine having capabilities compatible withthe RIP engine 420 from a plurality of the RIP engines included in theDFE 100. With this configuration, the job communication unit 421transmits the job data to the DFE 100 by designating the RIP engine thatis the same type of the RIP engine 420.

The job communication unit 421 transmits the job data such as a packageof PDL information and JDF information or a package of intermediate dataand JDF information to the DFE 100. Further, the PDL information orintermediate data can be transmitted to the DFE 100 separately from theJDF information, in which the PDL information or intermediate data canbe prepared as external resource data, and the JDF information caninclude universal resource locators (URL) indicating a storage area ofthe PDL information or a storage area of intermediate data. In thisconfiguration, the DFE 100 that receives the JDF information can accessthe storage area specified by the URL to acquire the PDL information orintermediate data.

A description is given of a fictional block diagram of the DFE 100 withreference to FIG. 6. When the DFE 100 receives job data from the HWFserver 4, the DFE 100 controls the received job, an execution of the RIPprocessing, and the digital engine 150. The HWF server 4 transmits thejob data to the DFE 100 and instructs the DFE 100 to execute a printoutput operation by using the digital engine 150. Therefore, the DFE 100can be used as a device to provide digital printing capability to theHWF server 4.

The job control capability performable by the DFE 100 is a process ofcontrolling a series of processes such as a reception of job data, ananalysis of JDF information, a generation of raster data, and a printoutput operation by the digital engine 150. The execution control of theRIP processing is a process of controlling the RIP engine to execute theRIP processing based on information generated by the analysis of the JDFinformation and PDL information.

The information generatable by analyzing the JDF information means thatinformation used for the RIP processing is extracted from the JDFinformation (FIG. 3), and is then converted to a data format processableby the DFE 100, which is referred to “job attribute in DFE” in thisdisclosure. By executing the RIP processing by using the job attributein DFE and the PDL information, the intermediate data and raster datacan be generated.

The control capability of the digital engine 150 is a process oftransmitting raster data and at least a part of the above described jobattribute in DFE to the digital engine 150, and executing the printoutput operation by the digital engine 150. These capabilities can beimplemented by each of units illustrated in FIG. 6. Each of the unitsillustrated in FIG. 6 can be implemented by activating the hardware(FIG. 2) by loading programs stored in the ROM 30 on the RAM 20 andexecuting the loaded programs by using the CPU 10.

As illustrated in FIG. 6, the DFE 100 includes, for example, a networkI/F 101, a DFE controller 110, and a display 102. The DFE controller 110includes, for example, a job receiver 111 including a plurality ofspecific job receiving units 112, a system controller 113, a job datastorage 114, a UI controller 115, a job controller 116, a JDF analyzer117, a RIP unit 118, a RIP controller 119, a RIP engine 120, an imagestorage 121, a printer controller 122, a device information manager 123,and a device information communication unit 125.

The DFE 100 can include a plurality of RIP engines therein, and each ofthe plurality of RIP engines is compatible with each of RIP engines ofother available devices. Specifically, each of the plurality of RIPengines of the DFE 100 is compatible with each of the RIP engines ofother available devices that may transmit job data to the DFE 100 in theHWF system. Since the HWF servers 4 a and 4 b include different RIPengines, a plurality of the RIP engines that compatible with the RIPengines of HWF servers 4 a and 4 b is disposed in the DFE 100.

The job receiver 111 includes the plurality of specific job receivingunits 112. In this configuration, each of the specific job receivingunits 112 receives job data from the HWF server 4 via the network I/F101, and each of the plurality of specific job receiving units 112respectively corresponds to each of the plurality of RIP enginesdisposed in the DFE 100. In this configuration, the specific jobreceiving unit 112 can be used as a specific receiver.

As described above, when job data is transmitted from the HWF server 4to the DFE 100, the corresponding RIP engine 120 is designated, and thejob data is transmitted to the corresponding RIP engine 120. Therefore,the specific job receiving unit 112 in the job receiver 111,corresponding to the designated RIP engine 120, can receive the jobdata.

In the above described configuration, the job data can be input to theDFE 100 from the HWF server 4 via a network. Further, the job data canbe input to the DFE 100 via a portable memory such as a universal serialbus (USB) memory. In this disclosure, the JDF information is included inthe job data. If the JDF information is not included in the job data,the job receiver 111 generates dummy JDF information, and assigns thedummy JDF information to the job data.

The specific job receiving units 112 can be disposed for each of theabove described RIP engines 120. Further, each of the specific jobreceiving unit 112 can be used as a virtual printer set with jobcontents in advance. Specifically, each of the specific job receivingunits 112 can be disposed for the corresponding RIP engine 120 disposedin the DFE 100 and job contents, and then, by designating any one of theplurality of specific job receiving units 112, the corresponding job canbe executed with the contents set in advance.

Further, as to the one or more embodiment of the present disclosure, thespecific job receiving unit 112 can be set with a “pass-through mode.”As illustrated in FIG. 6, the DFE 100 can include the JDF analyzer 117,independently from the RIP engine 120, to perform an analysis of JDFinformation. When the “pass-through mode” is activated, the RIP engine120 performs an analysis of the JDF information while the analysis ofJDF information by the JDF analyzer 117 is not activated.

By employing this configuration having the “pass-through mode,” JDFinformation using a format not-processable by the JDF analyzer 117 canbe used, a RIP engine that is difficult to include JDF analysiscapability outside the RIP engine can be employed for the HWF server 4and the DFE 100. As to the one or more embodiments, the “pass-throughmode” may be used when a plurality of processes is distributed betweenthe RIP engine 420 disposed in the HWF server 4 and the RIP engine 120disposed in the DFE 100, in which the RIP engine 120 and the RIP engine420 employs the same type of engine having the same capabilities. TheRIP engine 120 can be used as an output-side image drawing informationgenerator, an output-side drawing information generator or a secondimage drawing information generator, in which the RIP engine 120generates the raster data as second image drawing information.

When the RIP processing is performed by the HWF server 4 and the DFE 100as the distributed processing, it is preferable that the RIP processingis performed as one sequential processing as much as possible withoutbeing perceived as separate processing by the HWF server 4 the DFE 100.Therefore, when data that is processed to the middle of the entireprocessing by the HWF server 4 is input to the DFE 100, it is preferablethat the processing is performed by the DFE 100 as a process beingcontinued from the HWF server 4 by omitting the JDF analysis processthat is performed normally when unprocessed job data is input to the DFE100.

As to the one or more embodiments, the RIP engine having the samecapabilities is disposed in each of the HWF server 4 and the DFE 100,with which the above described RIP processing can be controlled andperformed preferably. Further, in this configuration, it is preferablethat data processed by one RIP engine is transferred to another RIPengine as it is, which can be preferably implemented by using the“pass-through mode.”

The system controller 113 stores the job data received by the specificjob receiving unit 112 in the job data storage 114, or transfers the jobdata received by the specific job receiving unit 112 to the jobcontroller 116. If the DFE 100 is devised to store the job data, thesystem controller 113 stores the job data in the job data storage 114.Further, if the JDF information includes a description whether the jobdata is to be stored in the job data storage 114 or not, the systemcontroller 113 performs the processing in line with the description.

The job data is stored in the job data storage 114, for example, when apreview of print contents is performed by the DFE 100. In this case, thesystem controller 113 acquires data of a print target included in thejob data, which is PDL information and intermediate data, from the jobdata storage 114 to generate preview data, and transfers the previewdata to the UI controller 115. With this configuration, the UIcontroller 115 controls the display 102 to display a preview of theprint contents on the display 102.

When the preview data is to be generated, the system controller 113transfers the data of print target to the job controller 116, andrequests the job controller 116 to generate the preview data. The jobcontroller 116 transfers the data of print target to the RIP unit 118 togenerate the preview data, and the job controller 116 receives thegenerated preview data, and transfers the generated preview data to thesystem controller 113.

Further, when an operator changes the JDF information for the DFE 100,the job data is stored in the job data storage 114. In this case, thesystem controller 113 acquires the JDF information from the job datastorage 114, and transfers the JDF information to the UI controller 115.With this configuration, the JDF information of the job data isdisplayed on the display 102, and the operator can change the JDFinformation by performing an operation on the display 102.

When the operator changes the JDF information by operating the DFE 100,the UI controller 115 receives the changed information, and reports thechanged information to the system controller 113. The system controller113 applies the received changed information to the target JDFinformation to update the target JDF information, and stores the updatedtarget JDF information in the job data storage 114.

When the system controller 113 receives the job execution instruction,the system controller 113 reads out the job data stored in the job datastorage 114, and transfers the job data to the job controller 116. Thejob execution instruction can be input from the HWF server 4 via thenetwork or the job execution instruction can be input by an operation ofan operator to the DFE 100. Further, if the JDF information is set with,for example, the execution time, the system controller 113 transfers thejob data stored in the job data storage 114 to the job controller 116when the set execution time has come.

The job data storage 114 is a memory or a storage area to store the jobdata, which can be devised, for example, by the HDD 40 illustrated inFIG. 2. Further, the job data can be stored in a memory or a storagearea connected to the DFE 100 via a universal serial bus (USB)interface, or can be stored in a memory device connected or coupled viaa network.

As described above, the UI controller 115 controls the display 102 todisplay information, and receives an operation of an operator to the DFE100. When the above described editing process is performed to the JDFinformation, the UI controller 115 interprets the JDF information, anddisplays contents of the print job on the display 102.

The job controller 116 controls the job execution when the job executioninstruction is transmitted from the system controller 113. Specifically,the job controller 116 controls the JDF analysis process by the JDFanalyzer 117, the RIP processing by the RIP unit 118, and the control ofthe digital engine 150 by the printer controller 122.

When the job controller 116 receives the job execution instruction fromthe system controller 113, the job controller 116 inputs the JDFinformation included in the job data to the JDF analyzer 117 to requesta conversion of JDF. The JDF conversion request is a request forconverting the JDF information described by a format used by an originalor initial generator of the JDF information to a format decodable orprocessable by the RIP unit 118.

By contrast, when the above described “pass-through mode” is designated,the job controller 116 acquires the JDF information included in the jobdata from the system controller 113, and inputs the acquired JDFinformation at it is to the RIP unit 118. The designation of“pass-through mode” can be described in the JDF information by using thespecific job receiving unit 112. Further, when the “pass-through mode”is designated by the specific job receiving unit 112, a “page mode” anda “sheet mode” can be also designated depending on the designated RIPengine 120.

The JDF analyzer 117 converts the JDF information described with theformat used by the original generator to the format decodable orprocessable by the RIP unit 118. The JDF analyzer 117 retains aconversion table therein, and extracts information required for the RIPunit 118 from information included in the JDF information, and convertsa description format of the extracted information based on theconversion table. With this configuration, the above described jobattribute in DFE can be generated.

FIG. 7 is an example of a conversion table retainable by the JDFanalyzer 117. As illustrated in FIG. 7, the conversion table correlatesa description format of JDF information and a description format of jobattribute in DFE. For example, information of “number of copies”illustrated in FIG. 3 is described as “A-Amount” in the original orinitial JDF information, and “A-Amount” is converted to a description of“number of copies” when generating the job attribute in DFE.

The job attribute in DFE can be generated by the JDF analyzer 117 basedon the conversion table of FIG. 7. The information described in the jobattribute in DFE includes, for example, “job information,” editinformation,” and “finishing information” indicated in FIG. 3.

The JDF analyzer 117 sets the “RIP control mode” to the job attribute inDFE when generating the job attribute in DFE. The “RIP control mode”includes the “page mode” and “sheet mode.” The JDF analyzer 117 assignsor allocates the “RIP control mode” based on a type of the specific jobreceiving unit 112 that has received the job data, job contents, and HWFsoftware program installed in the HWF server 4 used as a transmissionsource of the job data.

In the configuration described in this specification, condensed printingfor a print job can be set by using the “page mode.” The “RIP controlmode” will be described later in detail.

Based on the job attribute in DFE generated by the JDF analyzer 117, thejob controller 116 generates “RIP parameter,” and transfers the “RIPparameter” to the RIP controller 119 in the RIP unit 118 to execute theRIP processing. With this configuration, the RIP unit 118 can executethe RIP processing based on the “RIP parameter.”

FIG. 8 is an example of one set of RIP parameters of one or moreembodiments. The RIP parameters include, for example, “type ofinput/output data,” “data reading information,” and “RIP control mode”as header information. The “type of input/output data” designates thetype of input/output data such as JDF, PDL or the like. The designatableformat is, for example, JDF, PDL, text format, extension of image data,and intermediate data.

The “data reading information” includes information of a designationmethod and a designation position of reading position and writingposition of the input/output data. The “RIP control mode” is informationthat designates the “page mode” and “sheet mode.” The header informationfurther includes, for example, information of “unit” used in the RIPparameter, and information of compression method of data.

The “input/output image information” includes, for example, “informationof output image,” “information of input image,” and “information ofimage processing.” The “information of output image” includesinformation of, for example, format, resolution, size, color separation,color shift, and page orientation of output image data. The “informationof input image” includes information of, for example, format,resolution, page area, and color settings of input image data. The“information of image processing” includes information of, for example,an offset of enlargement/reduction algorism, an object area, and anoffset of halftone.

The “PDL information” is information related to PDL information used forthe RIP parameter. The “PDL information” includes information of, forexample, “data area,” “size information,” and “data arrangement method.”In this disclosure, the PDL information is data of print target in ajob, and includes intermediate data. The “data area” designatesinformation of an area where the PDL information is stored. The “sizeinformation” designates a data size of the PDL information. The “dataarrangement method” designates a data arrangement pattern in a memorystoring the PDL information such as “little big endian” and “bigendian.”

When the “pass-through mode” is used, the job controller 116 generatesthe RIP parameter based on the JDF information and PDL information orthe JDF information and intermediate data. In this case, each of itemsconfiguring the RIP parameter is set with information useable forreferring corresponding items in JDF information.

As illustrated in FIG. 8, the RIP parameter includes the “RIP controlmode.” The RIP controller 119 controls the RIP engine 120 based on the“RIP control mode.” Therefore, the sequence is set based on the “RIPcontrol mode.” As above described, the “page mode” and “sheet mode” canbe set as the “RIP control mode.”

The “page mode” and “sheet mode” are performed to a plurality of pagesto generate raster data. As to the “page mode,” the RIP processing isperformed for each page of the plurality of pages, and then raster datacondensing the plurality of RIP-processed pages on one single sheet isgenerated. As to the “sheet mode,” a plurality of pages are condensed ona single sheet at first, and then the RIP processing is performed foreach part (i.e., each page) on the single sheet to generate raster datacondensing the plurality of pages on the single sheet.

Further, when the “pass-through mode” is set, the “pass-through mode”can be designated in the “RIP control mode.” However, this is just oneexample. The “pass-through mode” can be described in any items otherthan the “RIP control mode.”

Further, the job controller 116 sets “RIP engine identificationinformation” in the RIP parameter. The “RIP engine identificationinformation” is information for identifying each one of the plurality ofthe RIP engines 120 included in the RIP unit 118. In this configuration,the same RIP engine is used in the HWF server 4 as the RIP engine 420,and in the DFE 100 as the RIP engine 120.

Therefore, the JDF information includes information for designating thespecific job receiving unit 112 as described above, and the designatedspecific job receiving unit 112 receives the job data. Each one of thespecific job receiving units 112 corresponds to any one of the RIPengines 120, and identification information of the corresponding RIPengine 120 is added to the received JDF information. Based on theidentification information of the RIP engine 120 added to the JDFinformation, the job controller 116 adds the “RIP engine identificationinformation” to the RIP parameter.

As to the RIP unit 118, the RIP controller 119 controls the plurality ofRIP engines 120 to perform each of the internal processes of RIPprocessing based on the input RIP parameters to generate raster data. Asto the HWF system of the one or more embodiments, since the RIPcontroller 119 may receive a plurality of print jobs from a plurality ofdifferent HWF servers 4, the RIP controller 119 is designed to processthe plurality of print jobs receivable from the plurality of differentHWF servers 4.

Each of the plurality of different HWF servers 4 may process data ofprint job differently. For example, the above described “page mode” and“sheet mode” of the “RIP control mode” may be differently set for eachof the different HWF servers 4. When one of the RIP engine 120 is setwith the “page mode,” and the condensed printing is to be performed bythe RIP engine 120, original page data corresponding to the condensingnumbers are designated sequentially.

By contrast, when another one of the RIP engines 120 is set with the“sheet mode,” and the condensed printing is to be performed by anotherRIP engine 120, all of original page data before performing thecondensing are designated, and then the RIP processing is performed forall of the original page data. Therefore, the methods of designatingparameters for the RIP engine 120 may become different for each of thedifferent RIP engines 120. This difference is not limited to the “RIPcontrol mode.” For example, differences may occur due to a difference offormat and processing of original data such as a difference ofprocessing of the margin of the original data.

To cope with the differences of the RIP engines 120, the RIP controller119 of the one or more embodiments performs a conversion process ofparameters designated to a specific RIP engine 120 depending on thespecific RIP engine 120 that is to perform a specific RIP processing.For example, when data of the “page mode” is input to the specific RIPengine 120 set with the “sheet mode,” parameters described by the “pagemode” are converted to parameters described by the “sheet mode.” Thecapabilities of the RIP engine 120 will be described later in detail.

The image storage 121 is a memory or a storage area to store raster datagenerated by the RIP engine 120. The image storage 121 can be devised,for example, by the HDD 40 illustrated in FIG. 2. Further, the imagestorage 121 can be a memory or a storage area connected to the DFE 100via a universal serial bus (USB) interface, or can be a memory deviceconnected or coupled via a network.

The printer controller 122 is connected or coupled to the digital engine150. The printer controller 122 reads the raster data stored in theimage storage 121, and transmits the raster data to the digital engine150 to execute a print output operation. Further, the printer controller122 acquires the finishing information included in the job attribute inDFE from the job controller 116 to control a finishing process.

The printer controller 122 can communicate information with the digitalengine 150 to acquire information of the digital engine 150. Forexample, when CIP4 standard is used, DevCaps standard is defined as theJDF information standard for communicating device property informationwith a printer. Further, printer information can be collected by using acommunication protocol such as simple network management protocol (SNMP)and a database such as management information base (MIB).

The device information manager 123 manages the device information suchas information of the DFE 100 and the digital engine 150. The deviceinformation includes, for example, information of the RIP engines 120included in the RIP unit 118, and information of the specific jobreceiving units 112 in the job receiver 111. Further, the information ofthe specific job receiving units 112 includes information of the abovedescribed “pass-through mode.” Further, the device information manager123 acquires vendor information from a vendor information managementunit 126 to be described later.

The device information communication unit 125 communicates the deviceinformation with the HWF server 4 via the network I/F 101 using acompatible format such as MIB and job messaging format (JMF). With thisconfiguration, the device information communication unit 415 of the HWFserver 4 can acquire the device information from the DFE 100, with whichinformation of the RIP engines 120 and information of the specific jobreceiving units 112 included in the DFE 100 can be set to a GUI settableand displayable on the client terminal 5.

As to the DFE 100, when the printer controller 122 controls the digitalengine 150, and then a print output operation is completed, the systemcontroller 113 recognizes the completion of the print output operationvia the job controller 116. Then, the system controller 113 reports thecompletion of a job to the HWF server 4 via the job receiver 111. Withthis configuration, the job communication unit 421 of the HWF server 4receives a report of the completion of the job.

As to the HWF server 4, the job communication unit 421 transfers thereport of the completion of the job to the job controller 413, and thenthe job controller 413 reports the completion of the job to the workflowcontroller 418. The transmission of the job data from the HWF server 4to the DFE 10 is executed by the workflow controller 418 based on aworkflow information.

When the completion of the job by the DFE 100 is recognized, theworkflow controller 418 controls a next process based on the workflowinformation. A process to be performed after performing the print outputoperation by the DFE 100 is, for example, a post-processing by thepost-processing apparatus 3.

A description is given of a fictional block diagram of the RIP engine ofthe one or more embodiments. FIG. 9 is a schematic diagram illustratinga fictional block diagram of the RIP engine 120 having the JDF analyzer117 used for the JDF analysis process. As above described, the RIPengine 120 can be a software module that executes each of the internalprocesses of RIP processing to generate raster data based on the RIPparameter illustrated in FIG. 8. The RIP engine 120 can be, for example,an Adobe PDF printing engine (APPE) provided by Adobe systems, but notlimited hereto.

As illustrated in FIG. 9, the RIP engine 120 is configured by a controlunit 201 and other units. The other units can be employed as extendedunits, which can be extended by a vendor. The control unit 201 executesthe RIP processing by using various capabilities that can be devised asthe extended units. Specifically, as illustrated in FIG. 9, the RIPengine 120 includes the control unit 201 and the extended units such asan input unit 202, a RIP parameter analyzer 203, a pre-fright processingunit 204, a normalize processing unit 205, a mark processing unit 206, afont processing unit 207, a color management module (CMM) processingunit 209, a trapping processing unit 210, a calibration processing unit211, a screening processing unit 212, an output unit 213, and arendering processing unit 218.

The input unit 202 receives an initialization request, and an executionrequest for the RIP processing, and reports the request to the controlunit 201. When the initialization request is received, the abovedescribed RIP parameter is also input to the control unit 201. When thecontrol unit 201 receives the initialization request, the control unit201 inputs the RIP parameter, received at the same time with theinitialization request, to the RIP parameter analyzer 203. Then, thecontrol unit 201 acquires an analysis result of the RIP parameter,computed by the RIP parameter analyzer 203, and determines an activationsequence of each of the extended units included in the RIP engine 120when the RIP processing is performed. Further, the control unit 201determines a data format generatable by performing the RIP processing,in which the data format can be any one of the raster image, previewimage, PDF, and intermediate data.

Further, when the control unit 201 receives the execution request forthe RIP processing from the input unit 202, the control unit 201activates each of the extended units included in the RIP engine 120based on the activation sequence that is determined when the controlunit 201 receives the initialization request. The pre-fright processingunit 204 checks validity of input PDL data contents. If the pre-frightprocessing unit 204 detects an illegal PDL attribute, the pre-frightprocessing unit 204 reports the illegal PDL attribute to the controlunit 201. When the control unit 201 receives this report, the controlunit 201 reports the illegal PDL attribute to an external module such asthe RIP controller 119 and the job controller 116 via the output unit213.

The pre-fright processing checks whether attribute information thatdisenables a processing by other modules included in the RIP engine 120is included in the received data. For example, the pre-fright processingchecks whether a font unable to be processed is designated or not.

The normalize processing unit 205 converts the input PDL data to PDF ifthe input PDL data is not PDF but PostScript. The mark processing unit206 applies graphic information of a designated mark, and superimposesthe graphic information at a designated position on an output targetprint image such as a target print image.

The font processing unit 207 extracts font data, and embeds the font toPDL data, and outlines the font. The color management module (CMM)processing unit 209 converts a color space of an input image to cyan,magenta, yellow, black (CMYK) based on a color conversion table set byInternational Color Consortium (ICC) profile. The ICC profile includescolor ICC information, and device ICC information.

The trapping processing unit 210 performs trapping processing. Whendifferent color regions are set adjacently via boundaries of thedifferent color regions, a gap may occur at the boundaries when apositional error occurs for the adjacently-set different color regions.The trapping processing expands each of the color regions to fill thegap.

The calibration processing unit 211 adjusts fluctuation of generatedcolor balance, caused by aging and individual difference of an outputdevice, to enhance precision of color conversion by the CMM processingunit 209. Further, the process by the calibration processing unit 211can be performed outside the RIP engine 120.

The screening processing unit 212 generates halftone dots in view of afinal output such as printed sheet. Further, the process by thescreening processing unit 212 can be performed outside the RIP engine120 similar to the calibration processing unit 211. The output unit 213transmits a RIP processing result to the outside of the RIP engine 120.The RIP processing result is any one of raster image, preview image,PDF, and intermediate data that are determined when the initializationis performed.

The rendering processing unit 218 performs a rendering processing togenerate the raster data based on the input data. Further, as to theconfiguration of FIG. 9, the processing of the mark processing unit 206,and the processing of the font processing unit 207 can be collectivelyexecuted by the rendering processing unit 218.

A description is given of another fictional block diagram of the RIPengine 120 with reference to FIG. 10. FIG. 10 is a schematic diagramillustrating another fictional block diagram of the RIP engine 120without using the JDF analysis process by the JDF analyzer 117. As abovedescribed, a case that the JDF analyzer 117 does not perform the JDFanalysis process means that the internal processes of RIP processing areperformed by the HWF server 4 and the DFE 100 as the distributedprocessing. Therefore, the HWF server 4 includes the RIP engine 420having the same configuration of the RIP engine 120 illustrated in FIG.10.

As illustrated in FIG. 10, most of the fictional block diagram of theRIP engine 120 not using JDF analysis process by the JDF analyzer 117are same as the fictional block diagram of the RIP engine 120 of FIG. 9.Hereinafter, portions different from the configuration of FIG. 9 aredescribed. Similar to FIG. 9, the units other than the control unit 201can be used as the extended units. Specifically, as illustrated in FIG.10, the RIP engine 120 includes the control unit 201 and the extendedunits such as the input unit 202, the pre-fright processing unit 204,the normalize processing unit 205, the mark processing unit 206, thefont processing unit 207, the color management module (CMM) processingunit 209, the trapping processing unit 210, the calibration processingunit 211, the screening processing unit 212, the output unit 213, a jobattribute analyzer 214, a RIP status analyzer 215, a RIP status manager216, a layout processing unit 217 and the rendering processing unit 218.

As to the configuration of FIG. 10, when the control unit 201 receivesan initialization request from the input unit 202, the control unit 201acquires the initialization request and the JDF information. Then, thecontrol unit 201 analyzes the JDF information and PDL information byusing the job attribute analyzer 214, and the control unit 201determines a process sequence of the extended units, and a data formatto be generated as a process result of each of the extended units sameas the configuration of FIG. 9.

As to the RIP engine 120 disposed in the DFE 100, data format obtainedas a process result by the RIP engine 120 often becomes the raster datato be input to the printer controller 122. By contrast, as to the RIPengine 420 disposed in the HWF server 4, data format obtained as aprocess result by the RIP engine 420 becomes different depending onpatterns of the distributed processing by the HWF server 4 and the DFE100. Therefore, the control unit 201 of the RIP engine 120 determinesthe data format (e.g., PDL information, intermediate data) of theprocess result based on an analysis result by the job attribute analyzer214.

Further, the control unit 201 analyzes the RIP status informationincluded in the JDF information by using the RIP status analyzer 215 tocheck whether one or more already-executed internal processes of RIPprocessing exist. If the already-executed internal process of the RIPprocessing unit exists, the corresponding extended unit is excluded fromthe target processing units of the RIP processing.

Further, the RIP status analyzer 215 can analyze the RIP status includedin the JDF information, and the RIP status analyzer 215 can similarlyanalyze the RIP status based on PDL information. In a case of analyzingthe PDL information, since the attribute information such as parameteris erased for the already-executed internal processes of RIP processing,it can determine which one or more of the internal processes of RIPprocessing are not yet performed based on the remaining attributeinformation.

The layout processing unit 217 performs the imposition process. Underthe control of the control unit 201, the RIP status manager 216 changesthe RIP status corresponding to each of the internal processes of RIPalready performed by each of the extended units to “Done”. The outputunit 213 transmits a RIP result to the outside of the RIP engine. TheRIP result is data having the data format that is determined when theinitialization is performed.

The rendering processing unit 218 of FIG. 10 performs the renderingprocessing to generate the raster data based on the input data same asthe configuration of FIG. 9. Further, as to the configuration of FIG.10, the processing of the mark processing unit 206, the processing ofthe font processing unit 207, and further the processing of the layoutprocessing unit 217 can be collectively executed by the renderingprocessing unit 218.

Further, as described above, the plurality of the RIP engines 120disposed in the DFE 100 such as “DFE (engine A)” and “DFE (engine B)”can be selectively used depending on information of the “RIP devicedesignation” included in the JDF information. Since the control unit 201cannot consign the processing to the extended units of other RIP engine,the job controller 116 can be used to consign the processing.

As described above, the job controller 116 adds the “RIP engineidentification information” to the RIP parameter. In this case, the jobcontroller 116 generates different RIP parameters for each of thedifferent internal processes of RIP processing designated with differentRIP engines 120. In an example case of FIG. 3, the RIP parameter of“engine A” is generated or designated for executing the “font” and“layout,” the RIP parameter of “engine B” is generated or designated forexecuting the “mark,” and the RIP parameter of “engine A” is generatedor designated for the subsequent processes after the “mark” asillustrated in FIG. 3.

Then, the job controller 116 requests the RIP unit 118 to perform theRIP processing based on each of the generated RIP parameters with aprocess sequence set for each of the internal processes of RIPprocessing. With this configuration, each of the internal processes ofRIP processing can be performed by selectively using the different RIPengines such as “engine A” and “engine B.”

In this process, each of the engines can perform only the designatedprocess by referring the “RIP status” information. Specifically, bysetting the status of to-be-processed items as “NotYet” and the statusof other items as “Done,” only the designated process can be performed.

Further, as to the above described HWF system according to one or moreembodiments, the RIP engine 420 disposed in the HWF server 4 and the RIPengine 120 disposed in the DFE 100 employ the same RIP engine. In thisdisclosure, the same RIP engine means that the RIP engine has the sameconfiguration at least for generating the raster data.

Therefore, the RIP engine 420 and the RIP engine 120 may not employ thesame configuration for every one of the processing units illustrated inFIGS. 9 and 10. Specifically, the RIP engine 420 and the RIP engine 120employ the same configuration at least the one or more processing unitsillustrated in FIGS. 9 and 10 used for generating the raster data suchas the mark processing unit 206, the font processing unit 207, thelayout processing unit 217, and the rendering processing unit 218.Therefore, the RIP engine 420 and the RIP engine 120 employ the sameconfiguration for at least the processing units used for generating theraster data. Further, the RIP engine 420 and the RIP engine 120 canemploy the same configuration for other processing units as required.

A description is given of an operation of the HWF system of the one ormore embodiments with reference to FIG. 11. FIG. 11 is a sequentialchart of an operation flow of the HWF system. FIG. 11 is an example of asequential chart when the digital printer 1 executes a print outputoperation. As illustrated in FIG. 11, the device informationcommunication unit 415 of the HWF server 4 acquires device informationfrom the DFE 100 and the CTP 200 via a network, and the deviceinformation manager 416 registers the device information in the deviceinformation storage 417 (S1101). The process of S1101 can be performedat regular intervals.

When a registration of job data is performed by an operation of anoperator to a GUI of the HWF system, the client terminal 5 transmits ajob registration request to the HWF server 4 (S1102), in which the UIcontroller 412 of the HWF server 4 acquires the job registrationrequest. With this configuration, the data receiver 411 acquires jobdata under the control of the system controller 410 (S1103).

When the data receiver 411 acquires the job data, the system controller410 controls the job controller 413 to convert a format of the acquiredjob data to PDL format (S1104), and the format-converted job data isregistered in the job data storage 414. As to the GUI that theregistration of job data is performed at S1102, an interface such as afile path for designating a registration target data, and an inputsection for designating each of information items in the JDF information(FIG. 3) can be displayed.

Further, by performing the process at step S1101, the HWF server 4 canacquire information of the type of the RIP engine disposed in the DFE100. Therefore, the information of the “RIP device designation” (FIG. 3)can be selectively input to the input section on the GUI of the clientterminal 5, in which when the DFE 100 is to perform the processing, aspecific RIP engine to perform the concerned processing can be selected.

Further, when a process of dividing the job data is performed inresponse to an operation of the operator to the GUI of the HWF system,the client terminal 5 transmits a job dividing request to the HWF server4 (S1105). When the job dividing request is issued at S1105, theoperator designates the job dividing pattern as illustrated in FIG. 12.FIG. 12 is an example of information includable in the job dividingrequest transmitted at S1105. As illustrated in FIG. 12, informationindicating a dividing target job and information indicating dividingcontents are transmitted as the job dividing request. The informationindicating the dividing contents is information designating a device toexecute a print output operation for each one of pages.

In this example case, the information indicating dividing contents isspecifically correlated with a device to execute a print outputoperation of each of the dividing contents. In an example case of FIG.12, one device is correlated for executing a print output operation ofsome pages, and another device is correlated for executing a printoutput operation of other pages, in which the devices are correlatedwith the unit of “page.” The information indicated in FIG. 12 can beused as output destination designation information that designatesdifferent output destinations for different pages when the output targetimage includes a plurality of pages such as page data.

When the HWF server 4 receives the job dividing request, the systemcontroller 410 divides the dividing target job (i.e., job data)page-by-page based on the information indicating the dividing contents(FIG. 12) to generate a plurality of sub-job data configuring thedividing target job (S1106). In this process, the device designated foreach of the divided portions can be used as information of “devicedesignation” in the JDF information (FIG. 3). When the job data isdivided to generate the plurality of the sub-job data, each of the subjob data is stored in the job data storage 414 as a discrete job.

Further, when a process of generating a workflow is performed inresponse to an operation of the operator to the GUI of the HWF system,the client terminal 5 transmits a workflow generation request to the HWFserver 4 (S1107). When the workflow generation request is transmitted,information designating the workflow contents and informationidentifying one or more jobs to be processed in line with the workflowinformation (FIG. 5) are transmitted.

When the HWF server 4 receives the workflow generation request, thesystem controller 410 inputs the information received with the workflowgeneration request to the workflow controller 418. With thisconfiguration, the workflow controller 418 generates a new workflowinformation based on the received information, and stores the newworkflow information in the workflow information storage 419, andcorrelates the new workflow information and the job identified by theworkflow generation request (S1108). The workflow and the job can becorrelated by adding, for example, an identifier identifying theworkflow to the JDF information.

When a job execution operation is performed on the client terminal 5such as when the job execution operation is performed in response to anoperation of an operator to the GUI on the client terminal 5 afterS1108, the client terminal 5 transmits a job execution request to theHWF server 4 (S1109). Further, steps S1102 to S1109 can be performed asdifferent processes, or steps S1102 to S1109 can be performed asone-time process that performs the job registration request, jobdividing request, workflow generation request, and job execution requestas one operation.

When the HWF server 4 receives the job execution request, the systemcontroller 410 acquires the designated job data from the job datastorage 414 based on information for identifying the job data receivedwith the job execution request (S1110). Further, the system controller410 acquires the latest information of the device designated in theacquired job data from the device information manager 416, and sets theacquired latest device information to the job (S1111).

Then, the system controller 410 transfers the job data to the workflowcontroller 418 to start an execution of the workflow (S1112). Theworkflow controller 418 acquires the workflow information correlated tothe acquired job data from the workflow information storage 419, andexecutes the processes in line with the workflow information.

As to the workflow processing, the processing in the HWF server 4 to beperformed by the RIP engine 420 disposed in the HWF server 4 is executedat first (S1113). At S1113, under the control of the workflow controller418, the job controller 413 controls the RIP engine 420 to execute theprocesses as described above.

When the workflow processing proceeds to a stage to transfer theworkflow processing to the DFE 100, under the control of the workflowcontroller 418, the job controller 413 controls the job communicationunit 421 to transmit the job data to the DFE 100 (S1114). At S1114, thejob controller 413 designates one of the specific job receiving units112 from the plurality of specific job receiving units 112 based oninformation designated in the JDF information.

When the job data is transmitted to the DFE 100, any one of theplurality of specific job receiving units 112 is designated, in whichthe specific job receiving unit 112 matched to the job data receives thejob data in the DFE 100. When the job data is input into the DFE 100, asdescribed above, the RIP processing and the output processing by thedigital engine 150 are performed in the DFE 100 (S1115).

When the DFE 100 completes the designated processes, the job receiver111 reports the completion notice of the processes to the HWF server 4(S1116). When the job controller 413 receives the completion notice ofthe processes from the DFE 100 via the job communication unit 421, thejob controller 413 reports the completion notice of the processes to theworkflow controller 418. Then, the workflow controller 418 transmits apost processing request to the post-processing apparatus 3 to execute apost-processing designated in the workflow executable after theprocessing at the DFE 100 (S1117).

At S1117, under the control of the workflow controller 418, the jobcontroller 413 controls the job communication unit 421 to transmit thepost processing request to the post-processing apparatus 3. Byperforming the above described processing, the operation of the HWFsystem completes.

A description is given of a detail of the internal processing in the DFE100 at S1115 (see FIG. 11) with reference to FIG. 13, which is a flowchart showing the steps of the processing in the DFE 100. As illustratedin FIG. 13, when the HWF server 4 transmit the job data to the DFE 100,the designated specific job receiving unit 112 receives the job data(S1301). After receiving the job data, the specific job receiving unit112 updates the JDF information to apply the discrete setting, set tothe specific job receiving unit 112, to the job data (S1302).

The above described “pass-through mode” can be also applied at S1302.The job data applied with the discrete setting is input to the systemcontroller 113, and then the system controller 113 stores the input jobdata in the job data storage 114 depending on the settings, and performsa preview processing via the UI controller 115 depending on an operationof an operator.

The job execution timing of the DFE 100 can be set as below. Forexample, the job is executed when the job execution of the DFE 100 isrequested by an operation of the operator, or when a timer counts theexecution time set in advance, the system controller 113 inputs the jobdata to the job controller 116. Then, the job controller 116 checkswhether the pass-through mode is set by referring the input job data(S1303). If the result is not the pass-through mode (S1303: NO), the jobcontroller 116 outputs the job data to the JDF analyzer 117 to generatethe job attribute in DFE (S1304).

If the result is the pass-through mode (S1303: YES) or the job attributein DFE is generated by performing the JDF conversion (S1304), the jobcontroller 116 generates the RIP parameter (S1305). If the result is notthe pass-through mode (S1303: NO), the RIP parameter illustrated in FIG.8 is generated at S1305. By contrast, if the result is the pass-throughmode (S1303: YES), the RIP parameter is generated for information otherthan “input/output image information” among the information illustratedin FIG. 8, and the JDF information is referred for the “input/outputimage information.”

When the job controller 116 generates the RIP parameter (S1305), the jobcontroller 116 inputs required information to the RIP unit 118 toexecute the RIP processing. In this sequence, when the RIP controller119 performs the above described parameter conversion (S1306), the RIPcontroller 119 designates the converted parameters to the RIP engine120, and instructs the RIP engine 120 to execute the RIP processing(S1307). With this configuration, the raster data can be generated bythe RIP engine 120.

At S1305, as described above, based on information of the “RIP devicedesignation” illustrated in FIG. 3, the RIP parameter can be generatedfor each one of the RIP engines. At S1307, the RIP processing isexecuted for each of the generated RIP parameters with a given processsequence to generate the raster data.

When the raster data is generated, and the job controller 116 acquiresthe raster data from the RIP unit 118, the job controller 116 inputs theraster data to the printer controller 122 to execute a print outputoperation by using the digital engine 150 (S1308). With this processingconfiguration, the internal processing in the DFE 100 is completed.

A description is given of a detail of the RIP processing at S1307 ofFIG. 13 with reference to FIG. 14. As illustrated in FIG. 14, based onthe initialization request input to the input unit 202, the control unit201 performs an initialization process (S1401). In an example case ofFIG. 9, at S1401, the RIP parameter analyzer 203 receives and analyzesthe RIP parameter, and determines one or more extended units to be usedfor executing one or more processes among the extended units included inthe RIP engine 120, and a process sequence of processing of the extendedunits as described above. Further, the RIP parameter analyzer 203determines a data format of data to be generated as a process resultwhen the processing is performed.

Further, in another example case of FIG. 10, the job attribute analyzer214 receives and analyzes JDF information and PDL information todetermine one or more extended units to be used for executing one ormore processes among the extended units included in the RIP engine 120,and a process sequence of processing of the extended units. Further, thejob attribute analyzer 214 determines a data format of data to begenerated as a process result when the processing is performed. Then, inanother example case of FIG. 10, the control unit 201 instructs the RIPstatus analyzer 215 to execute the status analysis.

As to the RIP status analysis, the RIP status analyzer 215 refers orchecks the “RIP status” (FIG. 3), and selects one item of the internalprocesses of RIP processing (S1402). If the status of the selected itemis “Done” (S1403: YES), the corresponding extended unit is excluded fromthe extended units determined as the execution targets at S1401 (S1404).If the status of the selected item is “NotYet” (S1403: NO), the sequenceproceeds to S1405.

The RIP status analyzer 215 repeats steps from S1402 to S1405 until allof the items of the internal processes of RIP processing is processed(S1405: NO). When the RIP status analyzer 215 completes steps from S1402to S1405 for all of the items of the internal processes of RIPprocessing (S1405: YES), and the input unit 202 acquires an executionrequest for the RIP processing (S1406: YES), the control unit 201controls each of the extended units to execute the RIP processing with agiven process sequence (S1407).

At S1407, the RIP processing is requested to one or more extended unitsdetermined at step S1401 and not excluded by the process at step S1404.Further, the RIP processing is requested to perform in line with theprocess sequence determined at step S1401. When the one or more extendedunits perform the RIP processing and the raster data is generated, theoutput unit 213 outputs a process result (S1408). With this processingconfiguration, the RIP processing by the RIP unit 118 completes.

In another example case of FIG. 10, steps S1402 to S1405 (i.e., statusanalysis) is performed only for the RIP engine 120 set with thepass-through mode because the status analysis is required when the RIPprocessing is divided and assigned for each of the HWF server 4 and theDFE 100 as described above.

Since the RIP engine disposed in the HWF server 4 and the RIP enginedisposed in the DFE 100 use the RIP engine having the substantially sameprocessing capabilities, the RIP processing can be performed as oneprocessing without recognizing a boundary of the HWF server 4 and theDFE 100. Therefore, it is preferable to input data processed by the RIPengine 420 of the HWF server 4 to the RIP engine 120 of the DFE 100 asthey are, in which the pass-through mode is suitable for the RIPprocessing because the JDF analyzer 117 disposed outside of the RIPengine 120 is not used.

However, this is just one example. Even if the pass-through mode is notused, the status analysis is required when the RIP processing is dividedand assigned to each of the HWF server 4 and the DFE 100. Specifically,when the RIP processing is divided and assigned to each of the HWFserver 4 and the DFE 100, the RIP processing already executed at the HWFserver 4 is required to be excluded from the RIP processing when the RIPprocessing is executed at the DFE 100.

Therefore, even if the RIP engine 120 is not set with the pass-throughmode, the RIP status analyzer 215 can be disposed to divide and assignthe RIP processing to each of the HWF server 4 and the DFE 100.Specifically, when the RIP processing is divided and assigned to each ofthe HWF server 4 and the DFE 100, the JDF analysis can be performed bythe JDF analyzer 117 at the DFE 100, and then the status analysis can beperformed by the RIP status analyzer 215 to determine which internalprocess of RIP processing is required to be processed.

Further, when the HWF system includes a plurality of HWF servers 4,differences may occur to the print results depending on the version ofthe RIP engine 420 installed in each one of the HWF servers 4 and theversion of the RIP engine 120 installed in the DFE 100.

For example, as indicated in FIG. 15, the HWF server 4 may include theRIP engine a having a version of “Ver.1” while the DFE 100 may includethe RIP engine a having a version of “Ver.2.” In this case, the DFE 100may be installed with a version information reporting module thatreports the version of the RIP engine 120 a in the DFE 100 to the HWFserver 4. When the version information reporting module reports theversion of the RIP engine 120 a installed in the DFE 100 to the HWFserver 4, the HWF server 4 can determine whether the version of the RIPengine 420 installed in the HWF server 4 and the version of the RIPengine 120 installed in the DFE 100 are different.

When the HWF system is configured with the HWF server 4 and the DFE 100,a plurality of vendors may provide a plurality of RIP engines disposedin the DFE 100. For example, as indicated in FIG. 15, the DFE 100 can beinstalled with the RIP engine “a,” the RIP engine “b,” and the RIPengine “c”, in which the RIP engine “a,” the RIP engine “b,” and the RIPengine “c” are associated with different vendors.

In this case, the version information reporting module is installed inthe DFE 100 so that information of all of the RIP engines extended byeach one of the vendors can be processed entirely. However, the versioninformation reporting module is required to be developed each time whenthe RIP engine includes a sub-module or when each one of vendors changesthe version of the RIP engine, with which the development of the versioninformation reporting module affects the operation of the HWF systementirely.

In view of this issue, a vendor information management unit 126 isinstalled in the DFE 100 as indicated in FIG. 16, in which informationdeveloped by each one of vendors and specifically set for each one ofthe RIP engines is stored in the vendor information management unit 126as a vendor information unit 128. Then, the device informationcommunication unit 125 acquires the vendor information associated witheach one of the vendors from the vendor information management unit 126via the device information manager 123, and reports the vendorinformation to the HWF server 4.

Therefore, the above mentioned development of the version informationreporting module is not required even if a new RIP engine 120 isinstalled in the DFE 100, and the version of the RIP engine 120installed in the DFE 100 can be reported to the HWF server 4 by reducingthe effect of the new RIP engine 120 to the entire operation of the HWFsystem.

FIG. 16 is a fictional block diagram of the vendor informationmanagement unit 126 of an embodiment of the present invention. Asindicated in FIG. 16, the vendor information management unit 126includes a vendor information management controller 127, and vendorinformation units 128 a, 128 b and 128 c. As above described, each ofthe vendor information units 128 a, 128 b and 128 c is the RIP deviceinformation set by each vendor of the RIP engine 120 installed in theDFE 100. The RIP device information is also referred to as informationitem.

Further, each of the vendor information units 128 a, 128 b and 128 cincludes an interface for identifying variable information section basedon the RIP device information set by each one of vendors. Hereinafter,the interface is referred to as a vendor information identificationinterface (I/F). When the vendor information unit 128 receives anacquisition request for the vendor information from the vendorinformation management controller 127, the vendor information unit 128identifies the variable information section including the vendorinformation by using the vendor information identification I/F based ona tag included in the RIP device information.

Therefore, the vendor information identification I/F can be used as an(identification information) identifying unit that identifiesidentification information used for identifying the vendor informationof the RIP engine 120. Further, the vendor information unit 128 can beused as an identification information unit that includes the vendorinformation associated with the corresponding RIP engine 120. In thisdescription, the identification information used for identifying thevendor information of the RIP engine 120 is also referred to asgenerator identification information.

The vendor information unit 128 converts information of size of thevariable information section, information of data format used for thevariable information section, and an address indicating a storage areaof the vendor information to a format decodable or readable by thevendor information management controller 127. The description formatused for the variable information section, the expression of the versionof the RIP engine may vary depending on each one of vendors of the RIPengines. Further, the data format used for the variable informationsection is, for example, text information or binary information. Whenthe text information is used for the variable information section, thecharacter code is transmitted.

FIG. 17 illustrates an example of contents of the RIP device informationof an embodiment of the present invention. As indicated in FIG. 17, theRIP device information includes information of the DFE 100, andinformation of the RIP engine 120 including the vendor information.

As indicated in FIG. 17, the information of the DFE 100 is describedwith the format that is not dependent on the vendor of the RIP engine120. By contrast, the vendor information includes a section extendableby the vendor of the RIP engine 120. As above described, the format usedfor description in the section extendable by the vendor may becomedifferent if the vendors are different.

Therefore, the vendor information unit 128 identifies the variableinformation section based on the contents of the RIP device informationby using the vendor information identification I/F. Specifically, thevendor information unit 128 converts information included in theidentified section to a format decodable or readable by the vendorinformation management controller 127, and transmits theformat-converted information to the vendor information managementcontroller 127.

FIG. 18 is a sequential chart indicating a flow of a process comparingthe versions of RIP engines at the HWF server 4. The comparing processcan be started when the system controller 410 designates the specificjob receiving unit 112 corresponded to the RIP engine 420 installed inthe HWF server 4, and then the system controller 410 transmits anacquisition request for device information to the DFE 100. A descriptionis given of the process of comparing versions of the RIP engines at theHWF server 4 with reference to FIG. 18.

In the HWF server 4, the device information communication unit 415designates the RIP engine 120 installed in the DFE 100, and transmits anacquisition request for the device information to the DFE 100 (S1801).When the job receiver 111 receives the acquisition request from the HWFserver 4 (S1802), the job receiver 111 inputs the acquisition request tothe specific job receiving unit 112 corresponded to the RIP engine 120that is designated at the HWF server 4 (S1803).

Then, the specific job receiving unit 112 transfers the acquisitionrequest to the vendor information management unit 126. When the vendorinformation management unit 126 receives the acquisition request, thevendor information management unit 126 identifies the correspondingvendor information unit 128 based on information of the designatedspecific job receiving unit 112 (S1804).

The vendor information unit 128 identifies the variable informationsection where the vendor information is described based on informationdefined for the vendor information identification I/F and a tag includedin the RIP device information (S1805), and converts information in thevariable information section to the format decodable or readable by thevendor information management controller 127. Then, the vendorinformation unit 128 transmits the converted information of the variableinformation section to the vendor information management controller 127.

The vendor information management controller 127 acquires the vendorinformation based on the information received from the vendorinformation unit 128 such as the size of variable information section,information of data format used for the variable information section,and the address indicating the storage area of the vendor information(S1806), and transmits the acquired vendor information to the deviceinformation manager 123. Therefore, the vendor information managementcontroller 127 can be used as an identification information manager.

The device information manager 123 adds the acquired vendor informationto the device information of the RIP engine 120 installed in the DFE 100(S1807), and inputs the device information added with the acquiredvendor information to the device information communication unit 125.When the device information communication unit 125 receives the deviceinformation from the device information manager 123, the deviceinformation communication unit 125 transmits the device information tothe HWF server 4 (S1808).

When the device information communication unit 415 of the HWF server 4receives the device information from the device informationcommunication unit 125 (S1809), the device information communicationunit 415 transfers the device information to the device informationmanager 416, and then the device information manager 416 stores theacquired device information in the device information storage 417(S1810).

When the system controller 410 acquires the device information from thedevice information manager 416, the system controller 410 acquires theversion information of the RIP engine 120 of the DFE 100 based on thevendor information included in the acquired device information (S1811).Then, the system controller 410 compares the version of the RIP engine420 installed in the HWF server 4 and the version of the RIP engine 120installed in the DFE 100 (S1812).

As to the above described HWF system, the version of the RIP engine 420installed in the HWF server 4 and the version of the RIP engine 120installed in the DFE 100 are compared based on the device informationacquired from the DFE 100 to detect the difference between the versionof the RIP engine 420 installed in the HWF server 4 and the version ofthe RIP engine 120 installed in the DFE 100. Further, as to the abovedescribed HWF system, the vendor information identification I/F thatidentifies the variable information section extendable by each one ofthe vendors is defined in the vendor information unit 128. Therefore,even if a new RIP engine 120 is installed in the DFE 100 and/or theversion of the RIP engine 120 is changed, the version information of theRIP engine can be managed without affecting other modules in the DFE100.

As to the above described HWF system, the version of the RIP engineinstalled in the image forming apparatus can be managed effectively andefficiently, with which the image forming apparatus can be operatedeffectively and efficiently.

Each of the functions of the described embodiments may be implemented byone or more processing circuits or circuitry. Processing circuitryincludes a programmed processor, as a processor includes circuitry. Aprocessing circuit also includes devices such as an application specificintegrated circuit (ASIC), digital signal processor (DSP), fieldprogrammable gate array (FPGA), and conventional circuit componentsarranged to perform the recited functions. Further, the above describedimage processing method performable in the image processing apparatuscan be described as a computer-executable program, and thecomputer-executable program can be stored in a ROM or the like in theimage processing apparatus and executed by the image processingapparatus. Further, the computer-executable program can be stored in astorage medium or a carrier such as compact disc-read only memory(CD-ROM), digital versatile disc-read only memory (DVD-ROM) or the likefor distribution, or can be stored on a storage on a network anddownloaded as required.

Numerous additional modifications and variations for the communicationterminal, information processing system, and information processingmethod, a program to execute the information processing method by acomputer, and a storage or carrier medium of the program are possible inlight of the above teachings. It is therefore to be understood thatwithin the scope of the appended claims, the description of presentdisclosure may be practiced otherwise than as specifically describedherein. For example, elements and/or features of different examples andillustrative embodiments may be combined each other and/or substitutedfor each other within the scope of present disclosure and appendedclaims.

What is claimed is:
 1. An image generation-output control apparatus inan image processing system for controlling an image generation andoutput operation based on an instruction received from a server in theimage processing system, the server being configured to control aplurality of processes performable by the image processing system, andcommunicable with a first image forming apparatus and a second imageforming apparatus in the image processing system, the server includingfirst circuitry including a first image drawing information generator togenerate first image drawing information based on output target imageinformation when performing an image forming operation for the outputtarget image information using the first image forming apparatus, theimage generation-output control apparatus comprising: second circuitryincluding: a plurality of second image drawing information generators,each having one or more capabilities compatible with one or morecapabilities of the first image drawing information generator of thefirst circuitry of the server, to generate second image drawinginformation based on the output target image information acquired fromthe server; an identifying unit to identify generator identificationinformation used for identifying one of the plurality of second imagedrawing information generators; an identification information unitincluding the generator identification information associated with oneof the plurality of the second image drawing information generators, andthe identifying unit; and an identification information manager tomanage the generator identification information, wherein theidentification information unit instructs the identifying unit toidentify the generator identification information when the servertransmits an acquisition request for the generator identificationinformation to the image generation-output control apparatus, whereinthe identification information manager manages the identified generatoridentification information by including the identified generatoridentification information in job information of the imagegeneration-output control apparatus.
 2. The image generation-outputcontrol apparatus of claim 1, wherein the identifying unit converts aformat of the identified generator identification information to aformat processable by the identification information manager, theidentification information manager acquires version information used foridentifying a version of one of the plurality of the second imagedrawing information generators installed in the image generation-outputcontrol apparatus based on the generator identification informationhaving the format processable by the identification information manager,and the identification information manager manages the acquired versioninformation by including the acquired version information in the jobinformation of the image generation-output control apparatus.
 3. Theimage generation-output control apparatus of claim 1, wherein thegenerator identification information used for identifying one of theplurality of the second image drawing information generators is used toidentify one of the second image drawing information generators used forprocessing the output target image information.
 4. A method ofcontrolling an image generation and output operation by using an imagegeneration-output control apparatus in an image processing system basedon an instruction received from a server in the image processing system,the server being configured to control a plurality of processesperformable by the image processing system, and communicable with afirst image forming apparatus and a second image forming apparatus inthe image processing system, the server including first circuitryincluding a first image drawing information generator to generate firstimage drawing information based on output target image information whenperforming an image forming operation for the output target imageinformation using the first image forming apparatus, the imagegeneration-output control apparatus including second circuitry includinga plurality of second image drawing information generators, each havingone or more capabilities compatible with one or more capabilities of thefirst image drawing information generator of the first circuitry of theserver, to generate second image drawing information based on the outputtarget image information acquired from the server, the methodcomprising: identifying generator identification information foridentifying one of the second image drawing information generators basedon an acquisition request for the generator identification informationreceived from the server; and managing the identified generatoridentification information by including the identified generatoridentification information in job information of the imagegeneration-output control apparatus.
 5. A non-transitory storage mediumstoring a program that, when executed by a computer, causes the computerto execute a method of controlling an image generation and outputoperation by using an image generation-output control apparatus in animage processing system based on an instruction received from a serverin the image processing system, the server being configured to control aplurality of processes performable by the image processing system, andcommunicable with a first image forming apparatus and a second imageforming apparatus in the image processing system, the server includingfirst circuitry including a first image drawing information generator togenerate first image drawing information based on output target imageinformation when performing an image forming operation for the outputtarget image information using the first image forming apparatus, theimage generation-output control apparatus including second circuitryincluding a plurality of second image drawing information generators,each having one or more capabilities compatible with one or morecapabilities of the first image drawing information generator of thefirst circuitry of the server, to generate second image drawinginformation based on the output target image information acquired fromthe server, the method comprising: identifying generator identificationinformation for identifying one of the second image drawing informationgenerators based on an acquisition request for the generatoridentification information received from the server; and managing theidentified generator identification information by including theidentified generator identification information in job information ofthe image generation-output control apparatus.